feat: bump revm #44
Open
feat: bump revm #44
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3 tasks
4 tasks
|
Marked this as ready for review, please move back to draft @klkvr if this is incorrect |
29 tasks
mattsse
approved these changes
Mar 27, 2025
DaniPopes
approved these changes
Mar 29, 2025
|
@zerosnacks can you confirm that this will only be merged once we're done with #44 ? |
|
It likely makes sense to merge once #44 is in a mergeable state as that will test the changes That said, the scope is minimal enough that is could be merged prior if it is a blocker for anything |
Not blocking, just wanted to get an idea since it was open & approved for a while now. Marking as blocked & we can decide when to merge |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Bumps revm to latest version. I've removed
CfgEnvfromBlockchainDbMetaas it seems unused and it's now generic overSpecIdwhich we ideally don't need to deal with on fork-db lavel.Solution
PR Checklist